Release 10.1A: OpenEdge Deployment:
WebClient Applications

Managing AppServer connections

To download as-needed application components from a codebase residing on an AppServer, WebClient, by default, creates a new connection to the AppServer, downloads the components, and terminates the connection.

Note: To download at-startup application components before the application starts, WebClient creates a new connection to the codebase server.

If you want, WebClient can keep the connection used for downloading as-needed application components open and reuse the connection to download additional components until no more remain to be downloaded. To enable this option, in the Application Assembler’s Codebase Locator window, check the Keep Connection Open toggle box.

And if you want, WebClient can download as-needed application components over an AppServer connection you already have open. (Perhaps your business logic and the codebase reside on the same AppServer, and you have already connected to this AppServer to access the business logic.) To enable this option, just after you connect to the AppServer, assign the connection’s handle to the SERVER attribute of the CODEBASE-LOCATOR handle.

If you do so:

The application has full responsibility for managing the connection.
The application configuration file’s information regarding the codebase server is not used.
If the connection breaks, the download fails.
If there is an outstanding ASYNC request on the handle of the existing connection at the moment WebClient needs it for the download, WebClient raises an error on the RUN statement.
Note: For this reason, Progress Software Corporation recommends that an AppServer connection used for ASYNC requests not be used for downloading application components.